Communication schema of online system and method of ordering consumer product having specific configurations

ABSTRACT

An online communication schema for communicating online vehicle orders is provided. The communication schema includes a customer request message, which includes an order message having order information, contact information and vehicle configuration. The order message includes a fleet order message, a retail order message, and a tagged order message. The communication schema further includes a lead message having lead information, contact information, vehicle configuration, and dealer information. The communication schema further includes an order confirmation message.

RELATED PATENT APPLICATIONS

This application claims the benefit of U.S. patent application Ser. No.09/561,644, filed May. 2, 2000, and entitled Method and System forConfiguring and Ordering Consumer Product, which claims benefit of U.S.Provisional Application Serial No. 60/163,755, filed Nov. 5, 1999, andentitled Automotive Internet Business Methods and Systems.

This application is related to co-pending U.S. application Ser. No.09/538,516, filed on Mar. 29, 2000, and entitled, “Communication Schemaof Online System and Method of Status Inquiry and Tracking Related toOrders for Consumer Product Having Specific Configurations.”

This application is related to co-pending U.S. application Ser. No.09/539,392 filed on Mar. 30, 2000, and entitled, “Online System andMethod of Locating Consumer Product Having Specific Configurations inthe Enterprise Production Pipeline and Inventory.”

This application is related to co-pending U.S. application Ser. No.09/542,413 filed on Apr. 4, 2000, and entitled, “Online System andMethod of Reporting Related to Orders for Consumer Product HavingSpecific Configurations.”

This application is related to co-pending U.S. application Ser. No.09/543,833 filed on Apr. 4, 2000, and entitled, “Communication Schema ofOnline Reporting System and Method Related to Online Orders for ConsumerProducts Having Specific Configurations.”

This application is related to co-pending U.S. application Ser. No.09/543,686 filed on Apr. 5, 2000, and entitled, “Online System andMethod of Ordering and Specifying Consumer Product Having SpecificConfigurations.”

This application is related to co-pending U.S. application Ser. No.09/543,860, filed on Apr. 5, 2000, and entitled, “Communication Schemaof Online System and Method of Locating Consumer Product in theEnterprise Production Pipeline.”

This application is related to co-pending U.S. application Ser. No.09/537,190 filed on Mar. 29, 2000, and entitled, “Online System andMethod of Status Inquiry and Tracking Related to Orders for ConsumerProduct Having Specific Configurations.”

TECHNICAL FIELD OF THE INVENTION

The present invention relates in general to the field of electroniccommerce and computer software systems. More particularly, the inventionrelates to a communication schema of online system and method ofordering consumer product having specific configurations.

BACKGROUND OF THE INVENTION

On-line shopping is quickly becoming the preferred means for obtainingconsumer products and services. More consumers, for example, are nowusing the Internet to browse, comparison shop and order productson-line. On-line shopping systems have made product information,including pricing and availability, readily available to consumers andhave facilitated the location and purchasing of desired products atlower cost and with added convenience.

Accordingly, many retailers have established “electronic store fronts”to offer all kinds of products ranging from clothes and groceries tocomputers and automobiles. Conventional electronic store fronts,however, are often modeled after traditional catalogs and are limited inthe information disseminated to the consumer. With typical electronicstore fronts, for example, a consumer is prompted to search for adesired product by entering one or more keywords. A search result ofrelevant items is then displayed along with a product description andprice. The customer then places the desired items in an “electronicshopping cart,” which the customer uses to place an order with theon-line merchant. If an item is not in the merchant's inventory, thecustomer is informed either immediately or within a prescribed period oftime. If the customer is dissatisfied or unwilling to wait or desires topurchase the item elsewhere, the customer then returns to the storefront or calls the on-line merchant to cancel or change the order.

Still other systems, such as Dell Computer Corporation's dell.com, allowconsumers to configure or customize selected products in accordance withavailable features or options. Dell.com, for example, allows a consumerto customize computer systems by allowing the consumer to select variousoptions, e.g., memory, hard drive, monitor, CD/DVD drives, video card,sound card, etc. An updated price is then obtained based on the selectedoptions. The configured system is placed in a shopping cart and an ordersubmitted by selecting a “checkout” option. Order status information canthen be obtained upon providing an order number and verification data.

A shortcoming of conventional systems, however, is that product statusand tracking information is available only after an order is placed. Noinformation is available to the consumer, prior to the placement of theorder, relating to the availability or status of a matching or similarconfigured product already in the product's manufacturing and deliveryprocess or so-called “product pipeline.” For example, conventionalsystems do not provide real-time information relating to inventory,in-transit stock, scheduled and unscheduled orders, etc., that mayinfluence the consumer's decision to order or not order the configuredproduct. Such information may be important to a consumer who may chooseto select or not select a particular option because of a lack ofinventory or delay in scheduled production. Also, in cases where time isof the essence, such information may be used to notify a customer thatthe configured product is not readily available. A new order cantherefore be placed or a preexisting one updated without the customerhaving to cancel a previously submitted order. The availability ofstatus and tracking information, prior to the placement of an order bythe consumer, can therefore be used to minimize the risk that thecustomer will become inconvenienced and dissatisfied with the merchant'son-line ordering services.

SUMMARY OF THE INVENTION

The aforedescribed limitations and inadequacies of on-line shoppingsystems are substantially overcome by the present invention. The presentinvention provides a method and system wherein a consumer is providedreal-time information, prior to the placement of an order or purchase bythe consumer, regarding the availability and status of a configuredproduct in relation to the product's manufacturing and delivery processor “pipeline.”

The present invention provides an on-line method and system wherein theproduct delivery time to a consumer is reduced by locating and “tagging”an available product already in a product pipeline. The presentinvention allows a consumer to locate and tag the desired product atvarious stages of the pipeline, including but not limited to scheduledand unscheduled order banks, final assembly, in-plant inventory,in-transit stock, dealer inventory, etc. A located product may betagged, for example, using a customer credit card, checking accountnumber or electronic voucher or gift certificate.

The present invention provides an on-line method and system wherein theconsumer configures a product as required and places a product orderwhen no acceptable matches are found in the product pipeline.Alternatively, pre-existing or even canceled orders can be modified asrequired to fulfill the product order.

The invention also provides an on-line method and system whereinexpected delivery dates are calculated and updated based upon theprogress of an ordered or tagged product through the product pipeline.

The present invention also provides an on-line method and system whereinreal-time pricing and comparison data is provided for individual productfeatures or options.

The present invention also provides an on-line method and system whereina consumer tracks the progress of an ordered product through the productpipeline. Real-time status can be provided as requested or automaticallyin accordance with the occurrence of a predefined or significant event.

The present invention provides an on-line method and system whereinconsumer preferences and trends are reported.

In one embodiment of the present invention, an online communicationschema for communicating online vehicle orders is provided. Thecommunication schema includes a customer request message, which includesan order message having order information, contact information andvehicle configuration. The order message includes a fleet order message,a retail order message, and a tagged order message. The communicationschema further includes a lead message having lead information, contactinformation, vehicle configuration, and dealer information. Thecommunication schema further includes an order confirmation message.

In another embodiment of the present invention, a communication schemaused in an online system enabling a user to place an online custom orderfor a vehicle is provided. The schema includes an order message, whichincludes order information, contact information, and vehicleconfiguration information. The vehicle configuration informationincludes a price, a make, a model, an engine specification, atransmission specification, an exterior paint color, a wheelspecification, a tire specification, a seat fabric specification, aninterior color, and an audio system specification. The schema furtherincludes a confirmation message generated in response to processing theorder message.

In yet another embodiment of the present invention, a communicationschema used in an online system enabling a user to place an onlinecustom order for a vehicle is provided. The schema includes an ordermessage, which includes order information, contact information, andvehicle configuration information. The vehicle configuration includes aprice, a make, a model, an engine specification, a transmissionspecification, an exterior paint color, a wheel specification, a tirespecification, a seat fabric specification, an interior color, an audiosystem specification, a drive specification, a cab specification, a bodystyle specification, a rear axle ratio specification, a pay load packagespecification, a wheel base specification, a roof color, a doorspecification, an accent color, a spare tire specification, a PEPspecification, an option package specification, and a stand alonepackage specification.

In yet another embodiment of the present invention, an online method ofcommunication for an online vehicle ordering system is provided. Themethod includes generating an XML order message including orderinformation, customer contact information, and vehicle configurationinformation, generating an XML confirmation message in response toprocessing the order message, the confirmation message including anorder number, a model year, a dealer identifier, an order receipt date,an order process date, and an order process time.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the present invention and the advantagesthereof, reference may be made to the accompanying drawings, in which:

FIG. 1 is a flow diagram showing a method for product ordering andtracking according to a preferred embodiment of the present invention;

FIG. 2 is a preferred embodiment of a system for implementing the methodshown in FIG. 1;

FIG. 3 is a block diagram of an embodiment of the web-based customvehicle ordering and tracking system constructed according to theteachings of the present invention;

FIG. 4 is a simplified flowchart of an embodiment of the web-basedcustom vehicle ordering and tracking method according to the teachingsof the present invention;

FIG. 5 is another flowchart of another embodiment of the web-basedcustom vehicle ordering and tracking method of the present invention;

FIG. 6 is a block diagram of another embodiment of the web-based customvehicle ordering and tracking system according to the teachings of thepresent invention;

FIGS. 7A-7C provide a more detailed block diagram of an embodiment ofthe web-based custom vehicle ordering and tracking system according tothe teachings of the present invention;

FIG. 8 is a more detailed block and flow diagram of an embodiment of theweb-based custom vehicle locate process according to the teachings ofthe present invention;

FIG. 9 is a more detailed block and flow diagram of an embodiment ofmessage processing of the locate process according to the teachings ofthe present invention;

FIG. 10 is a more detailed block and flow diagram of an embodiment ofmessage processing of the locate process according to the teachings ofthe present invention;

FIG. 11 is a more detailed block and flow diagram of an object-orientedembodiment of the web-based custom vehicle locate process according tothe teachings of the present invention;

FIG. 12 is a diagram of an embodiment of a search request message schemaaccording to the teachings of the present invention;

FIG. 13 is a diagram of an embodiment of a search result message schemaaccording to the teachings of the present invention;

FIG. 14 is a diagram of an embodiment of a tag request message schemaaccording to the teachings of the present invention;

FIG. 15 is a diagram of an embodiment of a tag response message schemaaccording to the teachings of the present invention;

FIG. 16 is a more detailed block and flow diagram of an embodiment ofmessage processing of the order process according to the teachings ofthe present invention;

FIG. 17 is a more detailed block and flow diagram of an embodiment ofnew order message processing according to the teachings of the presentinvention;

FIG. 18 is a more detailed block and flow diagram of an embodiment oftag order message processing according to the teachings of the presentinvention;

FIG. 19 is a more detailed block and flow diagram of an embodiment oflead message processing according to the teachings of the presentinvention;

FIG. 20 is a more detailed block and flow diagram of an embodiment ofcancel unscheduled order message processing according to the teachingsof the present invention;

FIG. 21 is a more detailed block and flow diagram of an embodiment ofcancel scheduled order message processing according to the teachings ofthe present invention;

FIG. 22 is a more detailed block and flow diagram of an embodiment ofspecification change message processing according to the teachings ofthe present invention;

FIG. 23 is a flowchart of an embodiment of an order number generatingprocess according to the teachings of the present invention;

FIG. 24 is a diagram of an embodiment of a customer request messageschema according to the teachings of the present invention;

FIG. 25 is a diagram of an embodiment of a fleet order message schemaaccording to the teachings of the present invention;

FIG. 26 is a diagram of an embodiment of a retail order message schemaaccording to the teachings of the present invention;

FIG. 27 is a diagram of an embodiment of a lead message schema accordingto the teachings of the present invention;

FIG. 28 is a block and flow diagram of an embodiment of a status processaccording to the teachings of the present invention;

FIG. 29 is a diagram of an embodiment of a customer status requestmessage schema according to the teachings of the present invention;

FIG. 30 is a diagram of an embodiment of a customer status reply messageschema according to the teachings of the present invention;

FIG. 31 is a diagram of an embodiment of a batch status request messageschema according to the teachings of the present invention;

FIG. 32 is a diagram of an embodiment of a batch status reply messageschema according to the teachings of the present invention;

FIG. 33 is a block and flow diagram of an embodiment of a report processaccording to the teachings of the present invention;

FIG. 34 is a diagram of an embodiment of a status report message schemaaccording to the teachings of the present invention;

FIG. 35 is a diagram of an embodiment of a order report message schemaaccording to the teachings of the present invention;

FIG. 36 is a diagram of an embodiment of a lead report message schemaaccording to the teachings of the present invention; and

FIGS. 37A-37C illustrate a diagram of an embodiment of a user sessionmessage format.

DETAILED DESCRIPTION OF THE INVENTION

As described above, there is a need to provide immediate feedback toon-line customers as to the availability of selected merchandise.Furthermore, it is advantageous to somehow satisfy the customer's ordereven when the selected item is not in inventory. Although these featuresare desirable for any on-line merchant, they are especially advantageousfor big-ticket items such as automobiles where a customer may chooseamong a myriad of options and features, and where a single completedsale translates to large dividends.

FIG. 1 is a flow diagram of a preferred method for ordering and trackingconsumer products. As shown in FIG. 1, a consumer desiring to purchase aproduct first selects and configures the product as desired based uponavailable product features or options, as shown in block 10. Dealerinventory and “in-process” product inventory are then searched to locateproducts that matched or substantially matched the consumer selectedproduct configuration, as shown in block 20. An in-process product isdefined as a product that is on the order bank to be manufactured, aproduct in the manufacturing process, or a product that is in transit tothe retail outlet or dealerships. If no matching or otherwise acceptableat-dealer or in-process product can be located, then the consumer isprovided the option to order the configured product, as shown in block30. If a matching or similar product is located, then the locatedproduct is “tagged” or designated for purchase and/or delivery to theconsumer. The consumer is then notified that a product has been locatedand tagged, and may be further notified that the actual purchase ordelivery of such product may be conditioned, for example, upon paymentor credit verification. The consumer may be warned that there is apossibility that the vehicle has been tagged or sold to someone who mayhave purchased the vehicle prior to the consumer's effort to locate andtag the vehicle. This may occur due to lag time in updating theinventory databases. The consumer is then provided an estimated productdelivery date. Real-time status and tracking information regarding theprogress of the ordered or tagged through the product pipeline is alsoprovided, as shown in block 40.

FIG. 2 is a block diagram of a system 100 for product ordering andtracking in accordance with the preferred method of FIG. 1. System 100includes consumer and product provider user interfaces 120 and 122,respectively, for communicating via networks 120 and 140 with dataprocessing system 110. A “consumer” or “customer” can be any purchaseror user of a product, and “product provider” can be, for example, aretailer, dealer or even manufacturer of the product offered for sale.The user interfaces 120 and 122 can be any suitable graphical userinterfaces for use over any Internet, intranet, extranet, or similarcommunication network. Communication networks 120 and 140 can bedifferent networks, or the same network. The data processing system 110,which is preferably embodied as one or more computer programs running ona suitable computer processor or processors, includes a configureproduct routine 112, a locate product routine 114, an order productroutine 116 and a status/tracking routine 118 for performing the methodof FIG. 1.

As further shown in FIG. 2, a product knowledge base 150 is used by thedata processing system to provide real-time configuration, ordering andtracking information to the consumer. Communication link 152, forexample, represents configuration and pricing data, business rulesand/or other like constraints limiting the options and configurationsavailable to the consumer. Inventory data, which includes, but is notlimited to, scheduled and unscheduled order banks, final assembly,in-plant inventory, in-transit stock, dealer inventory, is provided bythe knowledge base via link 154. Ordering rules and constraints,including information about the product's manufacturing and deliveryprocess, is provided via link 156. Status related data and rules arelikewise provided via link 158.

Further as shown in FIG. 2, system 110 can optionally include a reportprocess routine 119 for communicating customer trend, preference andother customer-related data to the provider of the product or productsoffered for sale. Reporting rules and constraints, such as privilege orsecurity data, is provided by product knowledge base 150.

FIG. 3 is a block diagram of a preferred embodiment of a system 310 forproduct ordering and tracking in accordance with the teachings of thepresent invention. Although the system 310 is shown as a web-basedsystem for ordering and tracking custom vehicles, the system 310 may bemodified as known and understood by those of skill in the art forordering and tracking various other consumer products over any intranet,extranet or other suitable type of communications network. System 310 inparticular provides on-line customers the ability to enter vehiclesearch criteria, and search for the vehicle in the dealership inventoryand in-process. If the search does not yield a vehicle satisfying thesearch criteria, then a customer may search for near-match vehicles orplace a custom order for the desired vehicle. In this way, the customeris provided immediate feedback as to the availability of the vehicle notonly in inventory but also in the pipeline at the manufacturer leadingto the dealer. The customer is also afforded satisfactory alternativesthat lead to the completion of a sale.

The system 310 of the present invention, by way of example and notlimitation, includes consumer “front end” 339, enterprise extranet 340,enterprise intranet 350 and enterprise data center 360. As shown in FIG.3, consumer front end provides consumer-to-business (C2B) functionality,enterprise extranet 340 provides business-to-business (B2B)functionality and enterprise intranet 350 and enterprise data center 360provide functionality internal to the enterprise, e.g., the productproviding entity. The various system components, however, can bedistributed within any of the segments 339, 340, 350 and 360 asrequired. FIG. 5, for example, shows another preferred embodiment of thepresent invention wherein a reporting data collector 342 and a reportingdata warehouse 346 are shown as part of the consumer front-end 539instead of the enterprise extranet 340 as previously shown in FIG. 3.

Referring again to FIG. 3, the consumer front end 339 includes one ormore portals or web sites 318 accessible over the World Wide Web (WWW)or the Internet 316 over which consumers 312 can access the system 310.The system can be accessed using browser software applications runningon client computers, machines or devices to download and access filescalled web pages stored on servers connected to the Internet. Using thesame browser applications, consumers can also enter and send informationto the servers. The Web pages can be single or multimedia documentscreated using hypertext markup language (HTML), extensible markuplanguage (XML), all of the HTML and XML variations and extensions,client-side scripting languages, cascading style sheets, Java appletsand serverlets, Active Server Pages (ASP), Cold Fusion, and otherlanguages and methods. Portals 318 may include a web page that is partof the manufacturer's web site (e.g. Ford.com) that contains links toother related web pages and content dedicated to system 310. Portals 318may also include customizable general purpose web pages that containshort summaries of current news, weather, financial news and serve as astarting point for many web surfers. Portals 318 may also include a website dedicated to automotive sales of one or more makers, or a web siteowned and operated by a dealership selling automobiles of one or moremakers. In this manner, portals 318 serve as a multimedia user interfacethat interfaces between the users and system 310.

Portals 318 are capable of accessing an inventory database 322 and aconfiguration and pricing database 324. Inventory database 322 containsdata related to the availability of any in-process or at-dealershipproduct that may match the specifications dictated by the consumer.Configuration and pricing database 324 contains data on vehicle modelsand the available configuration and options that may be specified by theconsumer. For example, a consumer may desire a white Ford Excursion withcream-colored leather seats, a V10 engine, premium aluminum wheels, andother options. Portal 318 is able to access configuration and pricingdatabase 324 and present the data to the on-line consumer so that theconsumer can indicate which configurations and options are desired. Theprice of the vehicle may be dynamically updated and displayed to reflectthe price of the vehicle with the selected vehicle configuration andoptions. The vehicle configurations and options may be grouped intopackages so that the on-line consumer may make his/her selection basedon the desired packages.

After the on-line consumer selects the vehicle make and model,configurations and options, he/she may submit the vehicle selection andperform a search in inventory to determine if one is currentlyavailable. Inventory database 322 receives its data from an inventoryimporter 328, which obtains inventory data from dealers 330 for theircurrent inventory. Dealers 330 may also represent any sales entity thathas an inventory of products for sale or lease to the public or tobusinesses. Inventory importer 328 further obtains data from aninventory packager 368 within the enterprise mainframe and data center360 of the manufacturer for data on vehicles in-transit from themanufacturing plant to the dealers, in manufacturing, and on the orderbank. Therefore the entire product pipeline is searched for a match or anear match, if so desired. If no match or near match is found, theconsumer may place a custom order for the vehicle. Inventory importer328 is responsible for obtaining the relevant data from one or moresources, reformatting the data as necessary, and storing the data ininventory database 322.

Portals 318 are also in communication with a sales processor 332, whichmay be owned and operated by a dealership organization or any entitythat operates as a retail outlet for the manufacturer. The vehicleselection information submitted by the consumer for purchase or lease isrelayed to sales processor 332 for processing. A financing processor 334may be used to receive and verify customer credit information and toprocess financing and complete the sale. A consumer who is not currentlyinterested in purchasing or leasing the vehicle may cause the vehicleselection information to be stored, such as at a prospect/buyer database336 or a database that is directly accessible by portals 318. Portals318 may recall the stored information when the same consumer visits theweb site again and allow the consumer to place the order at that time.

Sales processor 332 is also in communication with an order processor 352that may be part of an enterprise extranet 340 of the company.Communication between the sales processor 332 and the order processor352 is preferably done using an appropriate messaging scheme and messagerouters (not shown). Order processor 352 accepts submitted orders fromsales processor 332 and communicates the order to legacy databases 362in enterprise mainframe and data center environment 360 via a systemsnetwork architecture (SNA) server transmission control protocol/Internetprotocol (TCP/IP) gateway 356. Also in communication with salesprocessor 332 is a status request processor 354, which may reside in theextranet. Status request processor receives requests from salesprocessor 332 and obtains the order status from a status packager 364 inenterprise mainframe and data center environment 360. Status packager364 obtains status information from an enterprise vehicle informationsystem 366, which keeps track of in-plant and in-transit vehicleinventory as well as vehicles on the order bank. Order data database 372contains vehicle pricing information for vehicle configurations andoptions. A configuration packager 370 is operable to access order datadatabase 372 and provide this information to configuration/pricing datadatabase 324 at the front end.

Portals 318 are able to collect statistics and personal data on visitorsand report this data to a reporting data collector 342 in extranet 340.Traditional means of obtaining data on the visitors, such as usingcookie files, user entry forms, and the like may be used to collectdata. This data is then stored in a reporting data database 346 inintranet 350. A reporting data warehouse interface 344 is provided forusers who has authority to access the data in reporting data database346. Analysis on the collected may be performed to achieve a betterunderstanding of potential buyer likes and dislikes and to determinepotential buyer profiles.

For security reasons, firewalls separate the World Wide Web and theInternet from extranet 340, which is also separated from enterpriseintranet 350, and enterprise mainframe and data center 360 by firewalls.Account identifiers, user identifiers, passwords, etc. are needed toaccess the extranet, intranet and enterprise mainframe and data centersystems.

FIG. 4 is a simplified flowchart of an embodiment of the web-basedcustom vehicle tracking and ordering process 400 according to theteachings of the present invention. A user accesses a World Wide Web webpage, as shown in block 402. The consumer is then able to enter orselect from pull-down lists or other types of lists the vehicle make,model, color, configurations and options, as shown in block 404. System310 of the present invention then searches for vehicles matching theentered criteria in dealership inventory and in-process. Two alternatemethods of searching and locating a matching vehicle are shown in FIGS.4A-4B and FIG. 5.

Referring to block 106 in FIG. 4A, the system begins by first searchingin dealership inventory. The search may be performed by accessinginventory database 322. If a vehicle is not found, system 310 thensearches database 322 for matching vehicles that are in-transit, asshown in block 408. If a vehicle is not found, then system 310 searchesinventory database 322 for vehicles that are in-plant beingmanufactured, assembled, etc., as shown in block 410. If such a vehicleis still not located, then system 310 searches for a matching vehiclethat is on the order bank to be constructed, as shown in block 412. Allvehicles matching the search criteria are displayed, as shown in block414. If no vehicle matching the criteria is located, then near matchesare searched in inventory database 322 if so instructed by the consumer,as shown in block 416.

Referring to FIG. 5, an alternate method 430 of searching for andlocating a vehicle matching or substantially matching the enteredcriteria is shown. Similarly, the consumer accesses the system viaportal web pages, and enters desired vehicle configuration and options,as shown in blocks 432 and 434. Dealership inventory and in-processvehicles are searched for a match or near match, as shown in block 436.In block 438, all found vehicles are sorted according to how closely itmatched the entered search criteria, from highest percentage to lowestpercentage. The vehicles may further be sorted by status, for example,in-inventory vehicles are grouped together, in-transit vehicles aregrouped together, etc. The sorted found vehicles are then displayed tothe consumer, as shown in block 440.

Returning to FIG. 4B, if no match or near match is found, if theconsumer does not want to search for near matches, or the consumer isnot satisfied with any found vehicle in the search result, the consumermay indicate that he/she desires to place a custom order, as shown inblock 418. If the consumer does not desire to place a custom order atthis time, then the vehicle selection criteria may be saved in adatabase, such as prospective buyer database 336, as shown in blocks 420and 422. The process ends in block 424.

If, on the other hand, the search located a vehicle matching or nearlymatching the selection criteria, the consumer may “tag” or place a“hold” on the vehicle, as shown in block 440. In order to reserve avehicle, the consumer is asked to provide credit and/or other financialinformation, as shown in block 442. Typically, a consumer is asked toprovide a credit card account number from which a predetermined amountor a certain percentage of the vehicle price is charged to hold theselected vehicle. Alternatively, the consumer may opt to merely save thevehicle configuration and option selection and postpone the purchasingdecision until later, as shown in block 420.

In block 444, after the consumer has decided to hold a vehicle and haveprovided the credit information, a summary of the selected vehicle andthe transaction may be displayed to the consumer. This page may be savedor printed by the consumer as a receipt. In block 446, a vehicledelivery schedule projection may be displayed. The vehicle deliveryschedule may indicate that the vehicle is immediately available if it iscurrently on the lot of a dealership or in two months in the case of acustom order, for example. This step may also be performedsimultaneously with the search result information in block 414. Theconsumer may further select a means of reporting the vehicle deliverystatus and a frequency for the report, as shown in block 448. Forexample, the consumer may elect to receive status update reports viaemail, facsimile, or a web page. The status update reports may furtherprovide an updated delivery date, if it is changed from the originaldate due to changes in the manufacturing or transportation schedule. Theprocess ends in block 424.

FIG. 6 is an alternate embodiment 510 of the present invention similarto that shown in FIG. 3. It may be seen that the boundaries betweenconsumer front end 539, enterprise extranet 540, enterprise intranet550, and enterprise mainframe and data center 560 may be somewhatflexibly delineated, thus some of the system components may exist in theconsumer front end rather than the enterprise extranet, for example. Asshown in FIG. 5, reporting data collector 342 and reporting datawarehouse 346 may exist in consumer front end 539 instead of enterpriseextranet 540 and enterprise intranet 550, respectively. Further, orderprocessor 352 and status request processor 354 may reside in enterpriseintranet 550 rather than enterprise extranet 540.

Referring to FIGS. 7A-7C, a more detailed block diagram of an embodimentof the web-based custom vehicle ordering and tracking system 600according to the teachings of the present invention is shown. System 600includes multiple web sites or portals, such as BuyerConnection.com™ 602and Fleet.com™ 604, which provide an online interface to consumers 601and fleet consumers 603 via the Internet. These portals or web sitescommunicate with a web server 605, which processes consumer requests andgenerates responses thereto. For example, a consumer 601 may select anumber of options and features for the product (an automobile, forexample). A configuration engine 606 and configuration/pricing database608 are used to provide product configuration and pricing information.The consumer may then submit a search request to BuyerConnection.com 602to locate a vehicle with the selected options and features in dealerinventory, in-transit, in production, or on the order banks.BuyerConnection.com then generates a locate request and sends it to webserver 605 (L1). In one embodiment of the present invention, the locaterequest is an XML (extended markup language) message, that specifies aset of desired vehicle attributes or criteria, the relative importanceof each criterion, and the type of information to be returned by thesearch. For example, the response may be a summary of a list of vehiclesor detailed information of a few selected vehicles. Web server 605routes the search request to a locate inventory process 610, which isresponsible for locating the product which matches or nearly matches thesearch criteria submitted by the consumer.

Locate inventory process 610 accesses an inventory database 612, whichcontains the updated inventory data at all the dealerships and productsin-process (in-transit, in production, and on the order bank). Aninventory data importer 614 performs the inventory data import batchprocess in a periodic manner, such as nightly, to update the data ininventory database 612. Inventory data importer 614 may use a modemdial-up connection, file transport protocol (FTP) and/or other mechanismto pull inventory records from the dealerships. A data cleansing orinventory data verification process may be used to remove spellingmistakes and verify the VIN (vehicle identification number) against themake, model, and other features of the vehicle. The data cleansingprocess ensures that the inventory data is in a consistent and accurateformat that is suitable for consumer searching and display. Inventorydatabase 612 may be batch processed or updated in real-time as necessaryso that the most recent data is available for searching. Weekly fullextract may be performed in addition to nightly updates on new data.

A second input to locate process 610 and inventory database 612 is anenterprise vehicle information process 660, which contains and processesdata related to vehicles that are in-process. Locate inventory process610 searches inventory database 612 and returns a list of matches andnear matches (L2), preferably in decreasing order of matchingpercentile. The consumer may peruse the list and decide to tag a vehicleon the list. He or she can submit a tag request message (L3). The tagrequest message is sent from a workflow manager 622 to web server 605.The data in inventory database 612 associated with the selected vehicleis updated to indicate that it has been tagged and that subsequentsearches should yield results with the tagged vehicle suppressed.Preferably, a consumer is able to tag a vehicle only after a downpayment has been paid or the consumer's credit has been approved, forexample. A consumer may tag a vehicle that is in inventory, in-transit,in production, or on the order bank. A tag response message (L4) is thengenerated and returned to workflow manager 622 to confirm that theselected vehicle has been successfully tagged for purchase. The responsemay be formatted and displayed to the consumer to indicate success orfailure and perhaps also provide an estimate of the vehicle delivery oravailable date. A tag order message (O3) is generated and sent toworkflow manager process 622 for processing. Workflow manager process622 is one or more application servers which process vehicle orders andconveys this order to dealerships 624.

If the search response indicates that no match was found or the consumeris not satisfied with the near matches, the consumer has the option ofplacing a custom order for a vehicle with the desired options andfeatures (O1 or O2). Fleet orders (O1) placed by fleet consumers arerouted via web server 605 to a B2B server 640, which in turn sends theorder to an order process 644 via an intranet server 642. B2B server 640is preferably situated in an intranet environment behind a firewall thatsafeguards it from the outside world. Order process 644 processes thefleet order and then sends it to a corporate on-line communicationsentry point system (CONCEPS) 648 via an SNP server gateway 646. CONCEPSgenerates a new order, which is put on an order bank 656.

A retail order (O2) is also sent to workflow manager process 622, whichsends it to B2B server 640 and then to CONCEPS 648 via intranet server642, order process 644, and SNA server gateway 646. The new order isupdated in order bank 656.

CONCEPS 648 returns an order status or confirmation message (O5) thatconfirms the fleet or retail order. The order status message is routedto workflow manager process 622.

A consumer may also request for a lead on a dealer that may havevehicles he/she is interested in test driving, for example. TheBuyerConnection.com web site routes the consumer lead request (O4) toworkflow manager 622, which is sent to customer service representativesand to dealerships 624. The dealerships may then contact the consumerdirectly either by postal mail, electronic mail, or telephone.

The BuyerConnection.com web site 602, CarPoint 626, or otherpresentation applications may send a status query request message (Si)to workflow manager process 622. The status request message contains anorder source identifier (OrderSourceId) and a customer identifier(CustomerId), which are used by workflow manager 622 to identify all theactive orders for a customer. A common membership database 672 storessuch customer data for the presentation applications (portals and websites). A common membership database interface 670 may be used as aninterface between common membership database 672 and web server 605. Theworkflow manager then returns the status history for all vehiclesordered by the customer. The reply message (S2) is sent from Workflowmanager 622 to the presentation application.

Periodically, workflow manager process 622 sends a request for statusmessage (S3) to B2B server 640, which in turn is sent to a statuspackager 658 via a status translator 662 and intranet server 642. Theupdate request may be XML message that contains the order number, orderline number, and item number, which uniquely identify the order within aprospect/buyer database 630. The request message also may contain themodel year, body style, vehicle line, and dealer code, which uniquelyidentify the order in enterprise vehicle information system (NAVIS) 660until the vehicle is scheduled for manufacturing and a vehicleidentification number (VIN) is assigned to the vehicle. The VIN, statuscode, sub-status code, and estimated time of arrival are sent to statuspackager 658 residing on the mainframe. These values are compared withthe values in the mainframe systems and status packager 658 returns anydeltas or differences. This status request may be a batch process donenightly or every predetermined time period to update the status of theorders. A status information message (S4) is generated by statuspackager 658 and returned to workflow manager 622. The statusinformation message contains new values of fields that were found in themainframe systems that were different than what was in the statusrequest message.

A report process 666 is operable to access a report data warehouse 668and generate report data messages (R1 and R2) related to the retailorders and tagged orders, respectively, for reporting purposes. Thereport data are routed to BuyerConnection.com web site 602 via webserver 605. Dealer lead messages (R3) are generated through a customerrequest to have a dealer contact the customer about a certain vehiclethat the customer has selected online.

Locate Process and Locate Process Communication Message Schema

As described above, external applications are operable to submit searchrequests to locate process 610 to find vehicles in-process and atdealership which match or substantially match the search criteria. Thesearch requests may be submitted in the form of XML (extended markuplanguage) messages and the responses be received in an XML. The searchrequest messages contain the search criterion, the relative importanceor weight of each criteria, and the type of data to be returned. Aclient or presentation application may request information for a numberof reasons. For example, the client application may request a list ofidentifier and value pairs for a number of criteria, such as make andmodel of the desired vehicle. The returned values are then used topopulate the criteria definition elements of the client application userinterface, such as pull-down lists of available makes and models. Theclient application may then compile the user selected criteriapreferences into a second XML message that requests a list of matchingvehicles in inventory database 612. The returned response message may becompatible with known formats, such as the auto-lead data format (ADF).

Referring to FIG. 8, a message flow diagram of an embodiment of thelocate process according to the present invention is shown. The locateprocess includes a configure client 854 and a locate client 862 thatreside in a client side application 850, and a locate server 821 in theserver side application. A consumer calls up or downloads web pages 852to enter the desired make, model, options and features of the product, aconfigure message 853 is generated and sent to configure client 854. Theconsumer may also submit the same product criteria in a configuremessage 861 of the desired product via a web page 860 to search orlocate vehicles matching or generally matching the search criteria.Configure message 861 is sent to locate client 862, which generates alocate search request message 863 containing the configuration contentof configure message 861 and routes it to a locate server 821. Locateserver 821 parses and uses the search criteria in the locate searchrequest to query inventory database 612. Search results are thenreturned to locate server 821. Locate server 821 then generates aresponse message 865 containing a summary of the matched vehicles andsends it back to locate client 862. The returned response is parsed,formatted and stored in a database 869. The list of vehicles that matchor generally match the submitted criteria is then displayed as contentin a web page 855 to the consumer.

The consumer may then provide a selection input 856 of a particularvehicle from the list displayed in the web page, which sends a uniquevehicle identifier to locate client 862. Locate client 862 generates arequest message 866 containing the vehicle identifier, which is thenrouted to locate server 821. Locate server 821 sends a query toinventory database, 612 and data 867 is returned with more detailedvehicle information, which may include the URL (uniform resourcelocator) of a photographic image of the selected vehicle. Locate server821 then generates a response message 868 that includes the detailedvehicle information and routes it to locate client 862. The returneddetailed vehicle information is stored in cache 869 as well as displayedto the consumer in a web page 857.

The consumer may “tag” a selected vehicle after viewing the vehicleinformation to secure the right to purchase the vehicle. The consumergenerates a tag message 858 that contains the unique vehicle identifier,which is delivered to locate client 862. This may be accomplished byclicking on a link on the web page, which may be represented by theimage of the vehicle, for example. Locate client 862 then forwards thetag message to workflow manager 622. Workflow manager 622 sends atemporary tag to locate server 821. Locate server 821 then sends amessage 872 to data import database 614 to “hide” the selected vehicletherein. Data import database 614 replicates the tag and vehicleidentifier information 874 and sends it to inventory database 612.Locate server 821 further generates a tag confirmation message 876 andsends it to workflow manager 622 to indicate that the data associatedwith the selected vehicle has been updated to indicate that it has beentagged. The consumer may then complete the purchase of the taggedvehicle.

FIG. 9 is a locate server message flow diagram 900 according to anembodiment of the present invention. A listener 902 is preferably asecured XML listener on port 80 of locate server 821 that accepts XMLmessages sent from requesting presentation applications. Listener 902provides support for authenticating whom the request is from usingprivate key infrastructure (PKI) encrypted user credentials, forexample. Based on the requester's identity, listener 902 appliespre-assigned business rules to the request to allow or deny access tospecific functions and data sets supported by locate server 821.Listener 902 then sends the message to a parser 904.

Parser 904 reads the request messages and parses out specific portionsthereof, which are passed as parameters to the underlying searchprocesses via a dispatcher 906. Each parser 904 is persistent until aresponse is received from dispatcher 906. The content of the requestmessages generally includes request conditions or request criteria.Request conditions include required fields, optional fields, relevanceweights, maximum record count, etc. Request criteria include specificvehicle configuration, such as make, model, options, and features tosearch for. Two types of vehicle searches are supported, one thatreturns a summary of vehicles that fits the search criteria, and onethat returns detailed information of selected vehicles or a smallersubset of vehicles.

Dispatcher 906 examines the content of incoming parameters received fromparser 904 and determines which underlying locate server function isneeded to process the request. For example, the request may be a searchrequest for vehicles that match a set of criteria or a tag request on aparticular vehicle. Dispatcher 906 may examine the parameters againstbusiness rules defined for the requesting application, and replace anyoffending parameters with permissible parameters. Dispatcher 906 mayalso provide the overall locate server monitoring and control functionsfor spawning additional processes or threads to service incomingrequests, and to manage the overall creation and destruction of pooleddatabase sessions.

Searcher 908 is a locate server process that receives the incomingparameters from dispatcher 906 and converts them into an SQL (structuredquery language) query against inventory database 612. Searcher 908 usesthe passed parameters to select one or more vehicles that match orgenerally match the required field values, and then evaluate theoptional or preferred values of each vehicle. Weight factors may be usedto calculate a relevance value for each vehicle. The relevancecalculations are dynamic, and therefore can support any mix of weightedfactors and values, not only by application, but by individual requests.This allows applications to vary the weight factors to determine the mixthat most accurately returns a relevance based on their business needs,or alternatively, allow the consumers to provide their own relevancevalues.

Search values are returned from inventory database 612 to searcher 908,which passes the returned values to dispatcher 906 and then to parser904. Parser 904 constructs a response XML message and sends it to therequesting application.

Processing on the locate client side according to the teachings of thepresent invention is shown in FIG. 10. A message converter 922 isoperable to receive an XML document from the configure process andsearch criteria parameters as input to generate a locate request XMLformatted document output. Using message converter 922, applications arenot required to modify their application when new versions ofcommunication schemas are rolled out. Message converter 922 is alsooperable to accept text inputs to generate a locate request document. Asub-function of message converter 922 is a tag parser that createssupported tag messages and returns the status from the tag responsemessage.

A message client 924 is a multi-threaded HTTP (hypertext transferprotocol) process that provides the required functions to received theXML formatted document, then generates and sends XML messages andapplication credentials to and from the locate server.

A response parser 926 receives and processes the response XML documents.Response parser 926 outputs an ADO record set object that can easily beinserted into an application cache for paging, sorting or otherapplication specific data functions.

Referring to FIG. 11, a block diagram of an embodiment of a searchengine 962 of the locate process is shown. Search engine 962 includes atleast two layers or tiers—a business tier 964 overlaying a data tier966. Data tier 966 includes inventory database 612, which contains dataon enterprise-wide in inventory and in-process products. Data tier 966also includes a DataObj.InventorySimpleSearch object 976.DataObj.InventorySimpleSearch object 976 exposes a set of methods thatmay be called by business tier 964 to search inventory database 612.Business tier 964 includes a BusinessASP.Listener object 972 and aBusinessObj.BusinessObject object 974. BusinessObject object 974 is themain component that implements the business rules and validates userprivilege. The listener object 972 parses the request XML messagesreceived from the web sites and interprets the information for theBusinessObject. The listener object 972 is also operable to generate theXML reply messages. A Locate.ASP page 970 is operable to fetch therequest XML messages received from the web sites and passes it to thelistener object 972. Locate.ASP page 970 is also operable for pushingthe reply XML messages back to the web site that submitted the searchrequest messages.

A search request can be submitted to search engine 962 by using the HTTPby posting an XML request message to Locate.ASP page 970. Locate.ASPpage 970 may respond by returning a reply XML message containing thesearch results. The search request is contained in the body of an HTTPmessage and the search result is contained in the body of a returnedHTTP message. A valid user name and password with the necessaryprivilege is required to post a request to the Locate.ASP page 970.

A number of alternative means of initiating the locate search request isavailable depending on the operating system. For example, on the WindowsNT 4.0 platform, the request message may be posted using the Winlnet™API (application program interface), the WINSOCK™ API, or theMicrosoft.XMLHTTP™. Other means are available as known in the art.

Optionally, the search request message can be submitted to search engine802 by passing the XML message to a Business.Listener COM (common objectmodel) object. This object exposes a single method, ProcessXMLRequest,that accepts the XML message as a string.

Search engine 802 will accept a search request submitted by web sitesthat has a valid user name and password with the necessary privileges.Roles are assigned to the web sites that identify the web sites and itsavailable functionality. Business tier 804 verifies that the web sitehas the correct role to perform the requested task. A site role uniquelyidentifies the web site that is using the user name to request servicefrom search engine 802. For example, the BuyerConnection.com web site isrequired to have the SiteBuyerConnection role. The site role assignmentsare used to accomplish site-specific validations. A second role,functionality role, is used to identify the privilege of the user or website. For example, to search the dealer inventory database, the userneeds the FunctionalitySearchDealerInventoryDatabase role assignedthereto.

As described above, the locate processes involves generating and sendingXML messages in one embodiment, such as sending search request XMLmessages and search response XML messages. XML is primarily used tosupport application-to-application data exchange formats, such as thatfound in traditional EDI (electronic data interchange) over theInternet. The format of these XML messages are now described. It shouldbe noted that the XML implementation of the messages is but oneembodiment of the messaging schema, and that other languages andcommunication schemes can also be used.

In XML, tags are used to demarcate data content and data fields so thatthe content can be interpreted and manipulated. In XML, ELEMENT TYPEtags are used to define the various fields or parameters, a NAME tagsets out the name of the field, and a CONTENT tag sets out the datacontent of the field. Nested ELEMENT TYPE may be defined to describe amore complex data structure. For example,

<ElementType name=“Vehicle” content=eltOnly” order=“seq”>

<element type=“Identification”/>

<element type=“Status”/>

<element type=“DealerCode”/>

<element type=“ConfiguredModel”/>

<element type=“warranty”/>

</ElementType>

It may be seen that the vehicle field has five parameters that containsdata on the vehicle.

A search request message contains a specification of a set of vehicleattributes to be searched. For example, a search request message mayhave the format 1000 shown in FIG. 12. A search request tag 1002 is thetop level tag for the locate request. A request message may include manyrequest parameters that describe many attributes, with each followingthe same general format shown. Each search request 1002 includes acriteria tag 1004, which “wraps” all criterion 1006 for one searchquery. The valid values for criterion include dealer, make, model, andother options and features.

<ElementType name=“Criterion” content=“eltOnly” order=“seq”>

<Attribute Type name=“type” dt:type=“enumeration” dt:values=“vin dealermake model year package engine transmission tires exteriorpaintinteriortrim roofcolor seattrim accentcolor stage option msrp bodystylevehicletype category askingprice condition wheels audiotype”/>

<Attribute Type name=“required” dt:type=“boolean” required=“yes”/>

<Attribute Type name=“weight” dt:type=“number”/>

<attribute type=“type”/>

<attribute type=“required”/>

<attribute type=“weight”/>

<element type=“Value” minOccurs=“0” maxOccurs=“*”/>

<element type=“Range” minOccurs =“0” maxOccurs=“*”/>

</ElementType>

At least one criterion 1006 includes a value parameter 1008 and/or arange of values 1010 that specify the weight or relative importance ofthe criterion. Range of values 1010 is specified by a minimum value 1012and a maximum value 1014. Request 1002 further includes a selectparameter 1016 specified by an item parameter 1018. Select and itemparameters 1016 and 1018 are used to specify whether a vehicle summaryor vehicle detailed information is requested.

Referring to FIG. 13, an embodiment of the format of a search response1020 is specified by search results tag 1022. Search results tag 1022include an errors tag 1024 and a vehicles tag 1026. Errors tag 1024 isused to return information if the search is unsuccessful. Vehicles tag1026 contains data on one or more vehicle 1027 that fits the searchcriteria. An identification tag 1028 contains a unique VIN and/or stocknumber that is used to identify the vehicle. A status tag 1029 containsthe status of the vehicle, including condition, process tag, days ininventory, and description. A dealer code tag 1030 contains anidentifier that specifies the dealership that has the vehicle ininventory. Configured model tag 1031 is used to specify detailedinformation of the vehicle, including price information (type, value,currency) 1032, make (code, description) 1033, model (code, name, year,trim, description) 1034, engine specifications (code, displacement,number of cylinders, fuel type) 1035, transmission specifications (code,type, speed, description) 1036, exterior paint color (code, description)1037, wheel specifications (code, diameter, description) 1038, tirespecifications (code, manufacturer, description) 1039, seat trim color1040, interior trim materials 1041, audio system specifications (code,radio, cassette, CD, description) 1042, two-wheel or four-wheel drive1043, cab style 1044, body style 1045, rear axle ratio 1046, payloadpackage (extra payload or towing capacity) 1047, wheel base length 1048,roof color 1049, number of doors 1050, accent color (such as exteriorpaint color for the bottom half of the vehicle) 1051, spare tirespecification 1052, preferred equipment package (PEP) 1053, optionpackage 1054, stand alone options 1055, and any error message 1056.Lastly, warranty information is contained in a warranty parameter 1057.

A tag request message is sent from the workflow manager to the locateprocess in order to tag a vehicle for purchase. An embodiment of the tagrequest message format 1060 is similar to a tagged order message schema,which is shown in FIG. 14. Tag request format 1060 includes a top-leveltagged order tag 1061. Tag request message 1060 includes four additionaltags or parameters: order information 1062, contact 1072, credit cardauthorization number 1082, and tagged configuration 1084. Orderinformation 1062 includes the following parameters: order sourceidentifier 1063, session identifier 1064, order number 1065, order totalprice 1066, deposit amount 1067, order date 1068, order time 1069,dealer code 1070, and payment method 1071. Order source identifier 1063and session identifier 1064 are used to identify the web site andsession that submitted the order. Order number 1065 is a uniqueidentifier generated and assigned to the order.

Contact 1072 contains customer contact information, such as a uniquecustomer identifier 1073, name 1074, address 1075, email address 1076,daytime phone number 1077, evening phone number 1078, fax number 1079, afield 1080 describing the best method to contact the customer, and anyother comments 1081.

Credit card authorization number 1082 is the authorization numbergenerated in response to approving the use of the customer's credit cardto tag the vehicle for purchase.

The tagged configuration parameter 1084 contains data of the taggedvehicle: VIN 1085, stock number 1086, item number 1087, order linenumber 1088, matched configuration 1089, configured model 1090, taggeddealer 1121, selected dealer 1122, vehicle initial status 1123 (new,used, in-stock), and locate search identifier 1124. Stock number 1086 isa number assigned to the vehicle by the dealer, item number 1087 is anumber assigned to the vehicle by the enterprise mainframe. Matchedconfiguration 1089 is a Boolean value (true or false) that indicateswhether the tagged vehicle is exactly the same as the configuredvehicle. Locate search identifier 1124 identifies the taggedconfiguration selected by the customer to place an order. The configuredmodel 1090 parameter contains the same data on the configured vehicle,including prices 1091 (tag for price information), price 1092 (priceoffered to the Internet customer, manufacturer's suggested retail price,invoice price), make 1093, model 1094, engine specifications 1095,transmission specifications 1096, exterior paint color 1097, wheels1098, tires 1099, seat trim 1100, interior trim 1101, audio type 1102,drive 1103, cab 1104, body style 1105, rear axle ratio 1106, payloadpackage 1107, wheel base 1108, roof color 1109, number of doors 1110,accent color 1111, spare tire 1112, PEP 1113, PEP package content 1114,option package 1115, option package content 1116, stand alone optionstag 1117 for stand alone option 1118, errors tag 1119 for error 1120.

Tagged dealer 1121 is a tag for the dealer code of the dealer that hasthe requested vehicle. Selected dealer 1122 is the tag for the dealercode that the customer has selected from whom to purchase the vehicle.Vehicle initial status 1123 is the new, used, or in-stock status of thevehicle when it is tagged. Locate search identifier 1124 is used toidentify the tagged configuration selected by the consumer to place theorder.

In response to the tag request, a tag response message is generated. Thetag response schema may include the order number, order line number,item number, model year, dealer code, body style, VIN, stock number,status type, status, message, action code, receipt date, process date,and process time. The tag response message is returned to Workflowmanager as a confirmation that a vehicle has been successfully tagged inthe database for purchase.

Order Process and Order Process Communication Message Schema

Referring to FIG. 16, an overall data flow diagram for the order processaccording to an embodiment of the present invention is shown. Asdescribed above, the order process allows an Internet customer to submita lead to a dealership or purchase vehicle from dealer inventory,vehicles in-transit, or orders scheduled to be built. Order process 644receives an order number from a vehicle order application 1150, whichtypically resides at a web site, portal or is part of the portal.Vehicle order application 1150 also sends initial order information,initial credit card authorization information to workflow manager 622.Order process 644 places the order into the enterprise ordering system1158, which resides on the enterprise mainframes. Enterprise orderingsystem 1158 returns an item number and other order validationinformation to order process 644. Enterprise ordering system 1158 alsosends the item number and order validation information to a dealer 1160that either has the selected vehicle or will take delivery of thevehicle to the consumer. The item number, order number and ordervalidation information are also provided to a customer service process1164, which is operable to communicate with the customer 1162 viaseveral modes of communication. Dealer 1160 may also initiate change toan order by sending the change information to enterprise ordering system1158 as well as to workflow manager 622. The order change information isprovided to a reporting data collector 1154. Workflow manager 622 alsoprovides order status information to status module 1156.

FIG. 17 is a more detailed block and flow diagram of an embodiment ofnew order processing according to the teachings of the presentinvention. A consumer 601 submits a new order 1200 to a web site 602,which is constructed as an interface between the vehicle manufacturerand the customers. As described previously, the consumer has performed asearch and has selected a vehicle that satisfies the consumer'sselection criteria. Web site 602 retrieves vehicle configurationinformation 1201 from configuration and pricing database 608, andcustomer data 1202 from common membership database 672 via interface670. Web site 602 sends a request 1203 for credit card authorization toa credit card process 1232, which returns a credit card authorizationreply 1204 to web site 602. Web site 602 also sends an order numberrequest 1205 to an order number generator 620, which generates a uniqueorder number 1206 used to identify the order. Web site 602 provides anorder confirmation 1207 with the received order number to consumer,which is displayed on a web page. Web site 602 provides a new ordermessage 1028 to workflow manager 622, which forwards the new orderinformation 1209 to prospect/buyer database 630 and to B2B server 640 inthe form of a new order message 1210. B2B server 640 forwards new ordermessage 1211 to order process 644. Order process 644 then sends the neworder information 1212 to SNA server 646, which also sends the new orderinformation 1213 to CONCEPS 648. CONCEPS 648 forwards the new order 1214to order bank 656. CONCEPS 648 sends the dealer order data portion 1215of the new order to dealer order database 650. CONCEPS 648 then returnsedit results 1216 to SNA server 646, which forwards the information 1217to order process 644.

In response to receiving the CONCEPS edit results, order process 644sends an order confirmation message 1218 to B2B server 640. Orderprocess 644 may also request status action 1219 from a status actionlookup process 662, which returns a status action reply 1220. B2B server640 forwards the order confirmation message 1221 to workflow manager622. Prospect/buyer database 630 is then updated with initial orderstatus by workflow manager 622. Workflow manager 622 sends informationon the new order to dealer 624. Workflow manager 622 also sendsclean/dirty status 1224 to customer assistance center/businessassistance center, and customer service representatives (CAC/BAC CSR)632. Back at the enterprise mainframe, order processing re-edit process652 updates order bank 656, and updates dealer order information storedin dealer order database 650. Dealer order data 1227 is forwarded to adealer order process 654, which sends a dealer order receiptacknowledgement report. 1228 to dealer 624. Customer servicerepresentatives 632 is provided with follow-up and status updates 1229.Workflow manager 622 provides dealer 624 with periodic status updates.Dealer 624 sends a credit card payment request 1230 to workflow manager622, which forwards the request 1231 to credit card processor 1232.

FIG. 18 is a more detailed block and flow diagram of an embodiment oftag order processing according to the teachings of the presentinvention. A consumer 601 submits a tag order 1300 to web site or portal602, which is constructed as an interface between the vehiclemanufacturer and the customers. Web site 602 receives a vehicleconfiguration message 1301 from vehicle configuration and pricingdatabase 608 and receives information 1302 on vehicle inventory searchfrom locate process 610. Customer profile data 1303 are also stored intocommon membership database 672 via common membership database interface670. Web site 602 also submits a credit card authorization request 1304to a credit card processor 1220, which then returns a reply 1305. Website 602 also sends an order number request 1306 to order numbergenerator 620, which then returns a unique order number 1307. Theprocess by which the order numbers are generated is shown in FIG. 23 anddescribed below. Web site 602 then sends an order confirmation 1308 toconsumer 601 with the generated order number.

Thereafter, web site 602 sends a tag order message 1309 to workflowmanager 622, which forwards the new tag order information toprospect/buyer database 630. A temporary inventory tag message 1311 isthen sent from workflow manager 622 to locate process 610. A temporarytag is used initially when an Internet consumer requests to tag orreserve a vehicle. When a vehicle is temporarily tagged, it is notreturned in subsequent search results. Locate process 610 updates thedata in the inventory database and sends a tag response message 1312back as confirmation. Workflow manager 622 also informs dealer 624 bysending a new tag order 1313.

Periodically or when necessary, workflow manager 622 and dealer 624communicate to inform one another of inventory availability follow-up anstatus updates 1314. Prospect/buyer database 630 is updated by orderstatus updates 1315 from workflow manager 622. Workflow manager 622, atthe request of dealer 624 or consumer 601, may also send requestmessages 1316 to permanently tag or untag a vehicle in the database. Apermanent tag is typically submitted by a dealer through the workflowmanager to indicate that the transaction is completed on a vehicle thathad been previously temporarily tagged. A permanent tag message deletesthe vehicle from the inventory database. An untag message is used tocancel a temporary tag on a vehicle. The untag message allows thespecified vehicle to again be searched pursuant to subsequent searchrequests. An untag message may be submitted by a dealer, the CAC/BAC,CSR, consumer, or via locate administrative process that searches forexpired temporary tags. A temporary tag automatically expires after apredetermined period, such as 30 days, for example. Customer servicerepresentatives 632 also updates or is updated by dealer 624 regardinginventory availability follow-up and status updates 1317. Dealer 624also sends a credit card payment request 1318 to workflow manager 622,which sends the request 1319 to credit card processor 1220.

FIG. 19 is a more detailed block and flow diagram of an embodiment ofcustomer lead processing according to the teachings of the presentinvention. Consumer 601 requests 1330, from web site 602, information ona dealership, or a lead on the dealership. Vehicle configurationinformation 1331 is then retrieved from configuration/pricing database608 to web site 602. Web site 602 also stores or retrieves customerprofile data 1332 to or from common membership database 672. Web site602 sends a request 1333 for a lead number to a lead number generator1334. A lead number 1335 is generated and routed to web site 602. A leadconfirmation 1336 is sent to consumer 601 to provide the information onthe selected dealer. A lead message 1337 is then sent to workflowmanager 622, which stores the dealer lead information 1338 associatedwith the consumer in prospect/buyer database 630. The lead information1339 is also provided to dealer 624, so that the dealer may follow-up onthe lead with the consumer. Dealer 624 may report to workflow manager622 with lead follow-up and status update information 1340, when dealer624 follows up 1341 with consumer 601. Lead status update information1342 is provided to prospect/buyer database 630. Dealer 624 alsoprovides customer service representatives 632 lead follow-up and statusupdate information 1343.

An unscheduled order may be cancelled as shown in the block and dataflow diagram shown in FIG. 20. As opposed to a scheduled order, anunscheduled order is one that is initiated by the consumer and notpreviously planned or scheduled by the enterprise. Consumer 601 sends acancel request 1360 to dealer 624. Consumer 601 may also convey his orher desire to cancel the order via some communication 1361 to customerservice representatives 632, which conveys the cancel request 1362 todealer 624. Dealer 624 then submits a cancel message 1363 to CONCEPS648. In response, CONCEPS 648 updates order bank 656 with a cancelmessage 1364. Dealer 624 further sends a status update 1365 to workflowmanager 622, which forwards a status update 1366 to prospect/buyerdatabase 630.

A scheduled order may be cancelled as shown in the block and data flowdiagram shown in FIG. 21. Consumer 601 communicates his/her desire tocustomer service representatives 632 to cancel the order 1380. Inresponse, customer service representatives 632 communicate the cancelrequest to dealer 624 and also send a cancel request 1382 to a mech.spec. process 1382. Mech. spec. process 1382 sends a cancel message 1384to a MP&L process 1385. MP&L process 1385 in turn sends status updates1386 and 1388 to order bank 656 and enterprise vehicle informationprocess 660. Dealer 624 further sends a status update 1389 to workflowmanager 622, which forwards a status update 1390 to prospect/buyerdatabase 630.

The consumer may also change the specification of the vehicle whichhe/she has ordered. A block and data flow diagram of an embodiment ofthe specification change process is shown in FIG. 22. Consumer 601communicates 1400 a specification change request to dealer 624. Consumer601 may also convey his or her desire to cancel the order via somecommunication 1401 to customer service representatives 632, which conveythe specification change request 1402 to dealer 624. Dealer 624 thensubmits a specification change message 1403 to CONCEPS 648. In response,CONCEPS 648 updates order bank 656 with information on the specificationchanges 1404. Dealer 624 further sends a status update 1405 to workflowmanager 622, which forwards a status update 1406 to prospect/buyerdatabase 630.

FIG. 23 is a flowchart of an embodiment of an order number generator andprocess 1500 according to the teachings of the present invention. Ordernumber generator 1500 receives a request to generate an order number, asshown in block 1502. A determination is made as to the origin of therequest, as shown in block 1504, as any number of web sites authorizedto do business with the present system may generate this request. Inblock 1506, it is determined whether the request came from a first website, such as ford.com, buyerconnection.com or carpoint.com, forexample. If the first web site generated the order number request, thena predetermined constant, alpha, and a counter are used to generate anorder number, as shown in blocks 1507 and 1508. Similarly, for each website, a different set of alpha and counter are used to generate a uniqueorder number, as shown in blocks 1511-1515. In blocks 1518 and 1519, anencryption algorithm is used to encrypt the counter value. This is doneso that the Nth order does not get assigned an order number N. The ordernumber is then sent to the requester, as shown in block 1520. Theprocess ends in block 1521.

FIG. 24 is a message hierarchy diagram of customer request messages 1530sent from the consumer web site to the workflow manager according to theteachings of the present invention. There are at least two types ofcustomer request messages: an order 1532 and a lead 1533. There are atleast three types of messages conveying an order: fleet order message1534, retail order message 1535, and tagged order message 1536. A fleetorder message 1535 is used primarily to place an order encompassingmultiple vehicles. A tagged order message 1536 is used primarily toplace an order on a vehicle that was identified by the locate process.The selected vehicle may be in dealer inventory, in-transit, in-process,or on the order bank. A retail order message 1535 is used primarily toplace an order by a dealer. As discussed above, XML messaging or othercomparable means may be used for communicating the order informationbetween components in the present system.

Fleet order XML message 1535 includes three primary parameters: orderinformation 1537, fleet contact 1538, and fleet configuration 1539.Similarly, retail order XML message 1535 includes an order informationparameter 1540, a contact parameter 1541, a credit card authorizationnumber parameter 1542, and a retail configuration parameter 1543. Taggedorder message 1536 also includes an order information parameter 1544, acontact parameter 1545, a credit card authorization number parameter1546, and a tagged configuration parameter 1547. It may be seen thatthere is commonality between the message formats for the three types oforder messages. The detailed format of each order message is describedbelow.

The fleet order message includes a top level tag, FleetOrder 1560, andthree tags, OrderInformation 1562, FleetContact 1563, andFleetConfiguration 1564, at the next level. As described above,OrderInformation tag 1562 is used to include data related to the order,FleetContact tag 1563 is used to include data related to the contact orthe purchaser, and FleetConfiguration tag 1564 is used to include datarelated to the vehicle configuration of the ordered vehicles. The orderinformation parameters include order source identifier 1566, sessionidentifier 1567, order number 1568, order total price of the fleet 1569,deposit amount 1570, order date 1571, order time 1572, dealeridentification code 1573, and payment method 1574. The fleet contactparameters include the name of the contact person 1576, address 1577,email address 1578, daytime phone number 1579, and facsimile number1580.

The fleet configuration parameters include specifications on theconfigured model, which is the same or similar to the format used in thetag request message. The configured model parameters include priceinformation (type, value, currency) 1582 and 1583, make (code,description) 1584, model (code, name, year, trim, description) 1585,engine specifications (code, displacement, number of cylinders, fueltype) 1586, transmission specifications (code, type, speed, description)1587, exterior paint color (code, description) 1588, wheelspecifications (code, diameter, description) 1589, tire specifications(code, manufacturer, description) 1590, seat trim color 1591, interiortrim materials 1592, audio system specifications (code, radio, cassette,CD, description) 1593, two-wheel or four-wheel drive 1594, cab style1595, body style 1596, rear axle ratio 1597, payload package (extrapayload or towing capacity) 1598, wheel base length 1599, roof color1600, number of doors 1601, accent color (such as exterior paint colorfor the bottom half of the vehicle) 1602, spare tire specification 1603,preferred equipment package (PEP) 1604, PEP package content 1606, optionpackage 1607, option package content 1608, stand alone options 1609,stand alone package content 1610, and any error messages 1611 and 1612.

Another fleet configuration parameter is fleet data 1613, which containsinformation related to the fleet order. Another parameter is specialpaint options 1614, which contains additional exterior paint optionsthat the fleet customer may specify. Dealer special options parameter1615 allows the fleet customer to specify additional special options forthe vehicles. Price concession 1616 is used to provide information onany price concessions that may have been made to secure the fleet order.A note parameter 1617 allows additional information related to the fleetorder to be communicated. The next two parameters, narrative ship to1618 and narrative ship through 1619 are used to provide detailedinformation on shipping the vehicle fleet. The ship to and ship throughinformation includes name, street address, city, and state information.A pilot model inspection request parameter 1620 contains informationrelated to pilot model inspection, such as contact name, phone number,and date. A production request disclaimer 1621 is used to conveyinformation on the production request disclaimer, such as informationrelated to the approval or rejection of the disclaimer. A productionrequest parameter 1622 is used to communicate information on productionrequest, such as units, month, week, contact name, and contactinformation. Additional information may be provided in a remarksparameter 1623. The next parameter, order line number 1624, provides theline number for a given configuration within an order. A quantityparameter 1625 is used to communicate the number of vehicle ordered forthe fleet order. Lastly, a priority code parameter 1626 is a value usedfor production scheduling priority.

As shown in FIG. 26, the retail order message includes a top level tag,RetailOrder 1640, and four tags, OrderInformation 1641, Contact 1642,CreditCardAuthNum 1643, and RetailConfiguration 1644, at the next level.As described above, OrderInformation tag 1641 is used to include datarelated to the order, Contact tag 1642 is used to include data relatedto the contact or the purchaser, CreditCardAuthNum 1643 is used toinclude the credit card authorization number, and RetailConfigurationtag 1644 is used to include data related to the vehicle configuration ofthe ordered vehicles. The order information parameters include ordersource identifier 1648, session identifier 1649, order number 1650,total price of the order 1651, deposit amount 1652, order date 1653,order time 1654, dealer identification code 1655, and payment method1656. The contact parameters include information on the customer, suchas a customer identifier 1657, the name of the customer 1658, address1659, email address 1660, daytime phone number 1661, facsimile number1662, the best way to contact the customer 1664, and a field 1665 forincluding comments related to the customer.

The retail configuration parameters include specifications on theconfigured model, which is the same or similar to the format used in thetag request message and the fleet order message. The configured modelparameters include price information (type, value, currency) 1670 and1671, make (code, description) 1672, model (code, name, year, trim,description) 1673, engine specifications (code, displacement, number ofcylinders, fuel type) 1674, transmission specifications (code, type,speed, description) 1675, exterior paint color (code, description) 1676,wheel specifications (code, diameter, description) 1677, tirespecifications (code, manufacturer, description) 1678, seat trim color1679, interior trim materials 1680, audio system specifications (code,radio, cassette, CD, description) 1681, two-wheel or four-wheel drive1682, cab style 1683, body style 1684, rear axle ratio 1685, payloadpackage (extra payload or towing capacity) 1686, wheel base length 1687,roof color 1688, number of doors 1689, accent color (such as exteriorpaint color for the bottom half of the vehicle) 1690, spare tirespecification 1691, preferred equipment package (PEP) 1692, PEP packagecontent 1693, option package 1694, option package content 1695, standalone options 1696, stand alone package content 1697, and any errormessages 1699 and 1700.

Another retail configuration parameter is street address, city, andstate information. The next parameter, order line number 1701, providesthe line number for a given configuration within an order. Aconfiguration identifier 1702 is a unique configuration identifier thatspecifies the vehicle configuration selected by the customer in theorder. A quantity parameter 1703 is used to communicate the number ofvehicle ordered.

The lead message format is much like the fleet order and retail ordermessage formats. FIG. 27 shows an embodiment of the lead message formataccording to the present invention. The lead message includes a toplevel tag, lead 1720, and four tags, LeadInformation 1721, Contact 1722,RetailConfiguration 1723, and Dealer 1723, at the next level. Asdescribed above, LeadInformation tag 1721 is used to include datarelated to a dealer lead that the customer is requesting, Contact tag1722 is used to include data related to the customer desiring the leadinformation, RetailConfiguration tag 1723 is used to include datarelated to the vehicle configuration of the ordered vehicles, and Dealer1724 is used to include data related to the dealer.

The lead information parameters include a lead number 1725, a leadsource identifier 1726, session identifier of the online session withthe customer 1727, lead date 1728, lead time 1729, time frame forcontacting the customer 1730, and payment method 1731. The contactparameters include information on the customer, such as a customeridentifier 1732, the name of the customer 1733, address 1734, emailaddress 1735, daytime phone number 1736, evening phone number 1737,facsimile number 1738, the best way to contact the customer 1739, and afield 1740 for including comments related to the customer.

The retail configuration parameters include specifications on theconfigured model, which is the same or similar to the format used in thetag request message, the fleet order message, and the retail ordermessage. The configured model parameters include price information(type, value, currency) 1750 and 1751, make (code, description) 1752,model (code, name, year, trim, description) 1753, engine specifications(code, displacement, number of cylinders, fuel type) 1754, transmissionspecifications (code, type, speed, description) 1755, exterior paintcolor (code, description) 1756, wheel specifications (code, diameter,description) 1757, tire specifications (code, manufacturer, description)1758, seat trim color 1759, interior trim materials 1760, audio systemspecifications (code, radio, cassette, CD, description) 1761, two-wheelor four-wheel drive 1762, cab style 1763, body style 1764, rear axleratio 1765, payload package (extra payload or towing capacity) 1766,wheel base length 1767, roof color 1768, number of doors 1769, accentcolor (such as exterior paint color for the bottom half of the vehicle)1770, spare tire specification 1771, preferred equipment package (PEP)1772, PEP package content 1773, option package 1774, option packagecontent 1775, stand alone options 1776, stand alone package content1777, and any error messages 1778 and 1779.

Another lead retail configuration parameter is order line number 1742,provides the line number for a given configuration. A configurationidentifier 1743 is a unique configuration identifier that specifies thevehicle configuration selected by the customer in the order. A quantityparameter 1744 is used to communicate the number of vehicle the customeris interested in.

Lead message 1720 further includes a dealer parameter 1724. Dealerparameter 1724 is used to communicate information related to the dealerthat the customer desires to contact, such as a dealer identifier orcode 1745, the name of the dealer 1746, the address of the dealer 1747,and the phone number of the dealer 1748.

Status Process and Status Process Communication Message Schema

FIG. 28 is a block and flow diagram of an embodiment of statustranslator process 662 and status packager 658 which constitute thestatus process according to the teachings of the present invention. Thestatus process is operable to update, package, and deliver vehicle orderstatus information to consumer, intranet sales consultants, consumerservice representatives, and the prospect/buyer database. Periodically,such as nightly, workflow manager 622 sends a status update request tothe status process. In response, the status process sends batch dataupdate messages 1800 to workflow manager 622. the Status process alsosends batch status data updates 1801 to report process 666.

Status translator 662 receives the data updates from status packager658, which extracts the update information from the mainframe systems inthe enterprise. For example, status packager 658 extracts updateinformation from enterprise vehicle information process 660 and orderbank 656 in the corporate mainframe facility and data center, as shownin FIG. 7. Status packager 658 tracks at least one field in the datarecords for changes, and communicates the changes. Status packager 658matches certain data field contents in the orders with data fromenterprise vehicle information process 660 and order bank 656 to detectchanges to the order. For example, status packager 658 may track changesin the status code, sub-status code, produce date, shipped date, deliverdate, estimated time of arrival, and the establishment of a full 17position VIN, and reports the changes to status translator 662, whichthen reformats the data and sends it to workflow manager 622 and reportprocess 666. Workflow manager 622 then stores the data in prospect/buyerdatabase 630 (FIG. 7) Status packager 658 sends the status change datain a comma delimited flat file, for example, to status translator 662,which is then operable to translate it into an XML message, for example.In one embodiment of the present invention, the file transportcommunications mechanism between status packager 658 and statustranslator 662 is FTP (file transfer protocol) via WinINET, and themechanism between status translator and workflow manager 622 is XML viaHTTP.

Status translator 662 includes a communicator object 1802 and atranslator object 1804. Communicator object 1802 receives either an XMLmessage from workflow manager 622 or a comma delimited flat file fromstatus packager, and hands both to translator object 1804 for fileformat conversion from one to the other. Translator object 1804 thencarries out the file reformatting task and returns the converted file tocommunicator object 1802 for transmission to the appropriatedestination. Workflow manager 622 then uses the order number, order linenumber, and item number in the XML message to locate the specific orderrecord in buyer/prospect database. If a tag attribute, such as a changeflag, of the order is true, then certain data field contents are addedto the batch file as update data. For example, the status code,sub-status code, ETA, VIN, scheduled date, produced date, shipped date,delivered date, last update date, and last update time are added to thevehicle order status history in buyer/prospect database 630 if thechange flag attribute indicates that data has been changed.

An online consumer may send a status request message 1810 from aconsumer web site (shown as Ford of Canada in FIG. 28) to workflowmanager 622, which allows workflow manager 622 to respond to the requestwith data from prospect/buyer database 630. Using the order sourceidentifier and the customer identifier, workflow manager 622 extractsthe relevant record(s) in prospect/buyer database 630. The statushistory data for that active record is also returned as part of theresponse. Workflow manager 622 then sends the status data to theconsumer interface presentation application, i.e. the web site, fordisplay to the consumer.

FIG. 29 is a diagram of a consumer status query message schema accordingto the teachings of the present invention. The consumer status querymessage includes a StatusConsumerRequest tag 1820, which includes anorder source identifier (OrderSourceId) 1821 and a customer identifier(CustomerId) 1822. Order source identifier 1821 is used to identify thepresentation application, or the consumer web site, from which thestatus query was submitted. Customer identifier 1822 is used to identifythe online consumer that submitted the status query. Using these twoidentifiers, workflow manager 622 locates all active orders for thecustomer, and generates a reply message, the format of which is shown inFIG. 30. In an embodiment of the present invention, the status querymessage and the reply message are implemented in XML.

Referring to FIG. 30, the customer status request reply message includesa top level StatusConsumerReply tag 1830, which identifies the message,and a next level tag, StatusCOnsumerReplyorder 1831, which identifieseach order within the consumer status reply message. For each order,OrderNumber 1832 is used to identify the order. In addition, OrderDate1833, Vendor 1834, PriceLevel 1835, VehicleConfig 1836 also are used todescribe the transaction. A StatusHistory parameter 1837 is used toprovide information on the status and history of the order.StatusHistory 1837 includes ProduceDate 1838, ShippedDate 1839, andDeliveredDate 1840. StatusHistory further includes a StatusRecord tag1847, which includes the following fields or parameters: a status code1848 that represents the current status of the ordered vehicle,narrative text to describe the status code (StatusLiteral 1849),sub-status code 1851, ETA 1852, a scheduled date 1850 for delivery, VIN1853, the last update date 1854, and the last update time 1855.

FIG. 31 is a diagram of an embodiment of the batch status query messageaccording to the teachings of the present invention. The status batchrequest is sent from components in the system, such as workflow manager622, to status translator 662. The status batch request contains atop-level tag, StatusBatchRequest 1870, which includesStatusBatchRequestOrder tag 1871 to identifies each order within thestatus batch request message. The parameters for each vehicle orderincludes the order number 1872, order line number 1873, model year 1874,vehicle line 1875, body style 1876, dealer code 1877, item number 1878,status code 1878, sub-status code 1880, ETA 1881, VIN 1882, andScheduledDate 1883.

FIG. 32 is a diagram of an embodiment of a batch reply message schemaaccording to the teachings of the present invention. The status batchreply message includes a top level StatusBatchReply tag 1890, whichincludes a StatusBatchReplyOrder tag 1891 that is used to identify eachorder in the message. For each order, the following parameters areprovided: order number 1892, order line number 1893, model year 1894,vehicle line 1895, body style 1896, dealer code 1897, item number 1898,status code 1899, sub-status code 1901, ETA 1902, VIN 1903,ScheduledDate 1904, ProducedDate 1905, ShippedDate 1906, DeliveredDate1907, last update date 1910, and last update time 1911. Status code1899, substatus code 1901, ETA 1902, and VIN 1903 each further includesa change flag that is used to indicate whether change to the data hasbeen made.

Report Process and Report Process Communication Message Schema

FIG. 33 is a simplified block and flow diagram of report process 666according to the teachings of the present invention. Report process 666includes a data collector 1154, an OLAP (online analytical processing)server 1932, and a reporting web portal 1934. In operation, a useraccesses report processor 666 via reporting web portal 1934, whichcommunicates with OLAP server 1932. OLAP server 1932 contains formatteddata accessed from the raw data stored in report data warehouse 668.Report process 666 first authenticates the user by verifying that thegiven user identifier and password are valid. As the user requests aspecific report, whether the user has authorization to access therequested report is verified. A number of users may have access to thereports provided by report process 666, including online customers,dealers, enterprise engineers and managers, system administrators,system analysts and suppliers.

Report process 666 is operable to capture and store a variety of datafrom several components of the system, and then to display and printreports selected by the user. The consumer web sites 602 or thepresentation applications capture data generated by user activity at theweb site. For example, the user's click stream data and the sessionidentifier are captured. If the user invokes an auxiliary informationapplication at the web site to calculate the amount of interest on thecar loan, for example, then that information is also captured. If theuser generates a vehicle configuration, a configuration identifier willalso be generated and captured. At the end of a session, an XML messageis generated to include the entire session detailed data, identifiers,and click stream data, which is then sent to web server 605. Forexample, the XML message may include the web site identifier, sessionidentifier, configuration identifiers, customer zip code, auxiliaryinformation application invocation, configuration click stream for eachconfiguration identifier done during the session, vehicle configurationspecification for each configuration identifier, whether locate searchresults were selected, session start date and time, session end date andtime, and the entry point and exit points.

The transport of the session data message may be a pseudo-real time orbatch process that is run at the end of each session, or periodically,for example. Web server 605 then sends the messages to a report logutility of a report data collector 1154, which may perform some datacleansing function, such as parsing the message and correcting errors.Data collector 1154 then sends the update data to report data warehouse668 periodically, such as once a day, via batch feed, for example. Inaddition, a copy of all the XML messages generated in the presentationapplications and sent to workflow manager 622 are also routed to datacollector 1154. The messages include tagged orders, retail orders,leads, vehicle searches, session data, status updates, and lead/orderupdates.

After a complete configuration, the user may search the selectedconfiguration in inventory database 612. Locate process 610 is operableto pass a copy of the search result message to report log utility 1930.For each search results message, the session identifier, configurationidentifier, and the match relevance for each criteria, are provided tothe report process. Report data collector 1154 is operable to parse theXML message and extract the match relevance count for each criteria topass to report data warehouse 668.

When a retail order or a tagged order is placed, the order message isrouted to workflow manager 622 with the session identifier,configuration identifier, order number, and other order details. A copyof the order message is also routed, via web server 605, to datacollector 1154, which processes it and stores the data in data warehouse668. When workflow manager 622 receives order update messages from theorder process, a copy of the order update message is also routed to datacollector 1154 via web server 605. In addition, each time the status ofthe order is updated in workflow manager 622, a copy of the statusupdate message is also sent to data collector 1154.

When a configuration is sent as a request for a lead, a lead message isrouted to workflow manager 622, with the session identifier,configuration identifier, and other lead detailed data. A copy of thelead message is also routed to report data collector 1154 via web server605. Reporting data collector 1154 parses the XML lead message andstores the data in report data warehouse 668. Each time the lead data isupdated in workflow manager 622 because of dealer action, a copy of theupdate XML message is also routed to report data collector 1154.Alternatively, each time an order or a lead changes to an inactivestatus (sold, cancelled, future prospect) by dealer action, an updateXML message is generated to include a history of the associated dealerevents and sent to workflow manager 622 and report data collector 1154.

Dealer data is also provided to data collector 1154 for storage inreport data warehouse 668. Dealer data may include the dealer code, P&Acodes, dealer name, dealer address, dealer contact, dealer zip code,dealer zone, and dealer region. Report data warehouse 668 updates andgenerates metrics on the number of dealerships participating in theonline program. Similarly, credit process 1232 may also feed credit datato data collector 1154 for storage in report data warehouse 668. Inaddition, customer survey results 1930 which are used to gauge customersatisfaction are also stored in report data warehouse 668.

Report process 666 is operable to generate numerical and graphicalreports as requested by submitting standardized SQL to report database668. Exemplary reports are listed below:

Financial Reports

Compare revenue stream generated through the web sites by brand, make,model, model year, and model trim against orders placed online

Metrics to be broken down for time frame (month, week) and/or by regions

Free Demand Data Reports:

Metrics on end customer click streams on the web site forconfigurations, resulting in:

Abandoned

Retail Ordered

Tagged Order

Request-for-Quotes (Leads)

Searched

Saved in garage for future follow-up

Rank order of user “first clicks” - hot spots on the web sites, brands,etc.

Rank order of popular (non-standard) options per model/trim level

Rank ordered top 10 models per brand

Rank ordered most popular build combinations, configuration items(options or features), colors, etc.

Percentage of users selecting auxiliary services from the web sitesbased on model/trim configurations

Order Status Metric Reports

How long on average does it take to build a vehicle, a vehicle of acertain brand, make, trim, etc.

How does the promised delivery date compare with the actual deliverydate

Dealer Credit Metric Reports

How many credit applications by dealer, make, model, year

How many credit applications were approved, rejected, conditioned, andresulted in a purchase

Site/Application Performance Reports

Top-referring web sites

Metrics on exit points within the web sites

Metrics on web site traffic (number of user sessions, time, usage, etc.)

Number of requests per visit

Metrics on requests for credit and fulfillment percentage

Dealer Reports

Metrics on number of exact matches found

Metrics on new/used/pre-owned requests

Dealer inventory-related requests

Metrics on leads to dealers

Metrics on leads-to-close ratio

Metrics on initial dealer to closing dealer

Dealer Performance Reports

Participating dealers

Metrics on hits, leads, orders, etc.

Vehicle demand summary compared with regional average, etc.

Metrics on dealer response time on leads

Customer survey results

Locate, order and status module reports

Price Metric Reports

MSRP, dealer invoice, sold price, and ePrice trends, by dealer, by make,model, trim, etc.

Three message formats are used by the report process. FIG. 34 is adiagram of the messages. A StatusUpdate tag 2000 is the top level tagfor the messages, which includes two types of order messages 2001:tagged order 2002 -and retail order 2003. Another report message is alead message 2006.

FIG. 35 is a diagram of the order update message format, which may beimplemented in XML. Two kinds of orders 2001 are provided, tagged order2002 and retail order 2003. TaggedOrder 2002 includes order information(Orderlnformation) 2005, which includes order source identifier 2007,session identifier 2008, configuration identifier 2009, order number2010, VIN 2011, and item number 2012. TaggedOrder 2002 also includes thestatus of the order (OrderStatus) 2014, which includes status code 2015,status description 2016, time stamp of the order 2017, and status alert(ISCAlert) 2018.

TaggedOrder further includes dealer action data 2020, which includesdealer code 2021, first response metrics 2022, response type 2023,vehicle availability 2024, demo drive flag 2025, dealer action code2026, dealer action description 2027, and time stamp 2028. Firstresponse metrics 2022 is used to provide data that identifies the dealerresponse interval (hours, days, week, etc.), and response type 2023identifies the type of communications response the dealer takes(telephone call, email, etc.). DemoDriveFlag 2025 is a boolean parameterthat is used to indicate whether a demo drive has been taken or not.

RetailOrder 2003 also includes OrderInformation 2030, OrderStatus 2040,and DealerAction 2042 tags or parameters. OrderInformation 2030 alsoincludes order source identifier 2031, session identifier 2032,configuration identifier 2033, order number 2034, VIN 2035, and itemnumber 2036. DealerAction similarly includes dealer code 2043, firstresponse metrics 2044, response type 2045, vehicle availability 2046,demo drive flag 2047, dealer action code 2048, dealer action description2049, and time stamp 2050.

FIG. 36 is a diagram of the lead update message format 2006 according tothe teachings of the present invention. Lead message 2006 includes leadinformation 2060, lead status 2070, and dealer action 2080. Leadinformation 2060 includes the lead source identifier 2061, sessionidentifier 2062, configuration identifier 2063, and vehicle type 2064.Lead source identifier 2061 is used to indicate the originating web sitefrom which the request is submitted. Session identifier 2062 identifiesthe online session during which the dealer lead request was submitted.

Lead status 2070 includes status code 2071, status description 2072,time stamp 2073, and configuration change flag 2074. Configurationchange flag is a boolean parameter that indicates whether theconfiguration has been changed.

Dealer action 2080 is another parameter in the lead message format.Dealer action 2080 includes dealer code 2081, first response metrics2082, response type 2083, vehicle availability 2084, demo drive flag2085, dealer action code 2086, dealer action description 2087, and timestamp 2088.

FIGS. 37A through 37C illustrate a diagram of an embodiment of the usersession message format for transmitting user online session data to thereport process. A user session tag 2100 is the top-level tag of themessage. A session start parameter 2102 includes session ID 2103, avisitor descriptor 2104, a source application identifier 2105, a browserindicator 2106, an IP (Internet protocol) address 2107 of the user, anda reference 2108 field with additional description 2109 and IP address2110 parameters. A session end tag 2116 includes the session identifier2117, and a reason 2118 the session ended. A locale tag 2120 is used toprovide country 2121, language 2122, and currency type 2123 data. Acompare vehicles tag 2126 is used to provide data on the vehicles 2127the consumer comparison shopped. An end session tag 2128 is used toprovide signature 2129 data. A garage user action tag 2130 is used toprovide data on user activities related to the virtual online garage2131. The user's account identifier 2133 is provided by a login accounttag 2132. A notable decision tag 2136 is used to provide data on userdecisions, such as sequence reference 2137, description, and decision2139. A program decision tag 2140 is used to provide additional decisionrelated- data, such as sequence reference 2141, description 2142, anddecision 2143. A show tag 2150 provides signature 2151 and description2152 data on items, images or pages that the user chose to view. An useexternal application tag 2156 is used to provide signature 2157 anddescription 2158 data on auxiliary information applications invoked bythe user. An user input tag 2160 is used to provide signature 2161,description 2162, and input 2163 data on user online inputs.

Additional tags 2164-2167 are used to provide data related to creditapplication requests, credit application responses, quote requests, andquote responses. A locate request tag 2168 is used to provide anidentifier 2169 for the vehicle locate request, and a locate responsetag 2170 is used to provide an identifier 2171 for the locate response.Locate request details tag 2174 and locate response details 2177 areused to provide VIN 2175 and 2178 of the vehicle for which the userrequested detailed information. Furthermore, the identifiers 2181 and2185 associated with an order request 2180 and order response 2184 areprovided. The identifiers 2187 and 2190 associated with a status request2186 and status response 2189 are provided. A configuration changed tag2192 is used to provide sequence reference 2193, configurator identifier2194 and part 2195 data associated with the user changing vehicleconfigurations. A garage new user created tag 2200 is used to providesequence reference 2201 and login identifier 2202 associated with theuser action of parking a vehicle in a virtual garage for the first time.Garage user information changed tag 2204 provides sequence referencedata 2205. Garage loaded tag 2206 provides the sequence reference 2207,login identifier 2208, first login 2209 and login count 2210. Garageconfiguration saved tag 2212 provides sequence reference 2213, vehicle2214, and parts name list 2215 of the garaged vehicle. Garageconfiguration loaded 2216 tag provides sequence reference 2217, vehicle2218, parts name list 2219, and date saved 2220 of the vehicleconfiguration parked in the virtual garage. A new configurationgenerated tag 2222 is used to provide sequence reference 2223,configurator identifier 2224, and vehicle 2225 data on each new vehicleconfiguration generated by the user. A notable raised tag 2227 is usedto provide sequence reference 2228, description 2229, parts name list2230, and monetary value 2231 associated with the user activities. Apage state changed 2234 tag is used to provide sequence reference 2235,old page state 2236, and new page state 2237 data. A program begun tag2238 and program eligibility raised tag 2240 are used to provide dataassociated with the program. Description 2241 and reason 2242 data areprovided. A configured model tag 2243 is provided to include data on theconfigured vehicle.

Constructed and operating in this manner, a customer is afforded theopportunity to specify the desired configuration and options of aproduct to search the inventory for availability. The vehicleavailability anywhere along the pipeline from the manufacturer to thedealership may be determined. The customer may tag a vehicle that iscurrently anywhere in the pipeline that fits his/her criteria forpurchase. In the event that the specified product is not currentlyavailable, the customer may place a custom order for the product.Therefore, the customer is able to make a purchase on a product orvehicle that he/she desires and track the status of the vehicle when itis custom ordered and manufactured.

Several processes have been described that carry out the locate, order,status, and report functionalities of the system and XML communicationschema between the various components have been established.

Although the present invention has been described in the context ofcustom automotive vehicle inventory tracking and ordering, it is equallyapplicable to other products for which a consumer may select from amongdifferent configurations.

Although several embodiments of the present invention and its advantageshave been described in detail, it should be understood that mutations,changes, substitutions, transformations, modifications, variations, andalterations can be made therein without departing from the teachings ofthe present invention, the-spirit and scope of the invention being setforth by the appended claims.

What is claimed is:
 1. An online communication schema for communicatingonline vehicle orders, comprising: a computerized customer requestmessage comprising: an order message having order information, contactinformation and vehicle configuration, the order message comprising atleast one of a fleet order message, a retail order message, and a taggedorder message; and a lead message having lead information, contactinformation, vehicle configuration, and dealer information; an orderconfirmation message generated in response to processing the ordermessage and indicating at least the initiation of a purchase transactionof the selected vehicle by an identified dealer; and a lead confirmationmessage.
 2. The communication schema, as set forth in claim 1, whereinthe customer request message and order confirmation message are in XML.3. The communication schema, as set forth in claim 1, wherein the orderinformation comprises: an order source identifier; a session identifier;an order number; an order total price; a deposit amount; an order date;an order time; a dealer identifier; and a payment method indicator. 4.The communication schema, as set forth in claim 1, wherein the contactinformation comprises: a customer name; a customer address; a customeremail address; a customer daytime telephone number; and a customerfacsimile number.
 5. The communication schema, as set forth in claim 1,wherein the vehicle configuration comprises: a price; a make; a model;an engine specification; a transmission specification; and an exteriorpaint color.
 6. The communication schema, as set forth in claim 1,wherein the vehicle configuration comprises: a price; a make; a model;an engine specification; a transmission specification; an exterior paintcolor; a wheel specification; a tire specification; a seat fabricspecification; an interior color; and an audio system specification. 7.The communication schema, as set forth in claim 1, wherein the vehicleconfiguration comprises: a price; a make; a model; an enginespecification; a transmission specification; an exterior paint color; awheel specification; a tire specification; a seat fabric specification;an interior color; an audio system specification; a drive specification;a cab specification; a body style specification; a rear axle ratiospecification; a pay load package specification; a wheel basespecification; a roof color; a door specification; an accent color; aspare tire specification; a PEP specification; an option packagespecification; and a stand alone package specification.
 8. Thecommunication schema, as set forth in claim 7, wherein the fleet ordermessage further comprises: fleet data; special paint option data; dealerspecial option data; price concession data; vehicle shipping data; orderline number; and quantity.
 9. The communication schema, as set forth inclaim 8, wherein the fleet order message further comprises: a pilotmodel inspection request; a production request disclaimer; and aproduction request.
 10. The communication schema, as set forth in claim1, wherein the retail order message further comprises creditauthorization information.
 11. The communication schema, as set forth inclaim 4, wherein the contact information of the retail order messagefurther comprises: a customer identifier; an evening telephone number;and a best way to contact the customer information.
 12. Thecommunication schema, as set forth in claim 9, wherein the vehicleconfiguration of a tagged order message further comprises: a vehicleidentifier; a stock number; an item number; a dealer identifier of adealer having the tagged vehicle in inventory; a dealer identifier of adealer selected by the user from whom to purchase the tagged vehicle; avehicle initial status indicative of whether the vehicle is new or used;and a locate search identifier specifying the selected vehicleconfiguration.
 13. The communication schema, as set forth in claim 1,further comprising a tag status message generated in response toprocessing a tag order message.
 14. The communication schema, as setforth in claim 1, wherein the order confirmation message comprises: anorder number; an order line number; an item number; a model year; adealer identifier; a body style; an order status; an action code; anorder receipt date; an order process date; and an order process time.15. A communication schema used in an online system enabling a user toplace an online custom order for a vehicle, comprising: a computerizedorder message indicating a request to purchase a selected vehicle andcomprising order information, contact information, and vehicleconfiguration information; the vehicle configuration informationincluding: a price; a make; a model; an engine specification; atransmission specification; an exterior paint color; a wheelspecification; a tire specification; a seat fabric specification; aninterior color; and an audio system specification; and a confirmationmessage generated in response to processing the order message andindicating at least the initiation of a purchase transaction of theselected vehicle by an identified dealer.
 16. The communication schema,as set forth in claim 15, further comprising a lead message having leadinformation, contact information, vehicle configuration, and dealerinformation; and a lead confirmation message.
 17. The communicationschema, as set forth in claim 15, wherein the order message and orderconfirmation message are in XML.
 18. The communication schema, as setforth in claim 16, wherein the order information comprises: an ordersource identifier; a session identifier; an order number; an order totalprice; a deposit amount; p an order date; an order time; a dealeridentifier; and a payment method indicator.
 19. The communicationschema, as set forth in claim 15, wherein the contact informationcomprises: a customer name; a customer address; a customer emailaddress; a customer daytime telephone number; and a customer facsimilenumber.
 20. The communication schema, as set forth in claim 15, whereinthe vehicle configuration information further comprises: fleet data;special paint option data; dealer special option data; price concessiondata; vehicle shipping data; order line number; and quantity.
 21. Thecommunication schema, as set forth in claim 20, wherein the vehicleconfiguration information further comprises: a pilot model inspectionrequest; a production request disclaimer; and a production request. 22.The communication schema, as set forth in claim 15, wherein the ordermessage comprises credit authorization information.
 23. Thecommunication schema, as set forth in claim 15, wherein the contactinformation further comprises: a customer identifier; an eveningtelephone number; and a best way to contact the customer information.24. The communication schema, as set forth in claim 15, wherein thevehicle configuration further comprises: a vehicle identifier; a stocknumber; an item number; a dealer identifier of a dealer having thetagged vehicle in inventory; a dealer identifier of a dealer selected bythe user from whom to purchase the tagged vehicle; a vehicle initialstatus indicative of whether the vehicle is new or used; and a locatesearch identifier specifying the selected vehicle configuration.
 25. Thecommunication schema, as set forth in claim 15, wherein the confirmationmessage comprises: an order number; an order line number; an itemnumber; a model year; a dealer identifier; a body style; an orderstatus; an action code; an order receipt date; an order process date;and an order process time.
 26. An online method of communication for anonline vehicle ordering system, comprising: receiving a computerized XMLorder message indicating a request to purchase a selected vehicle andcomprising order information, customer contact information, and vehicleconfiguration information; and generating a computerized XMLconfirmation message in response to processing the order message, theconfirmation message indicating at least the initiation of a purchasetransaction of the selected vehicle by an identified dealer andcomprising an order number, a model year, a dealer identifier, an orderreceipt date, an order process date, and an order process time.
 27. Themethod, as set forth in claim 26, further comprising receiving a leadmessage having lead information, contact information, vehicleconfiguration, and dealer information in response to receiving a userlead request input.
 28. The method, as set forth in claim 26, whereinthe order information comprises: an order source identifier; a sessionidentifier; an order number; an order total price; a deposit amount; anorder date; an order time; a dealer identifier; and a payment methodindicator.
 29. The method, as set forth in claim 27, wherein the contactinformation comprises: a customer name; a customer address; a customeremail address; a customer daytime telephone number; and a customerfacsimile number.
 30. The method, as set forth in claim 27, wherein thevehicle configuration information further comprises: fleet data; specialpaint option data; dealer special option data; price concession data;vehicle shipping data; order line number; and quantity.
 31. The method,as set forth in claim 30, wherein the vehicle configuration informationfurther comprises: a pilot model inspection request; a productionrequest disclaimer; and a production request.
 32. The method, as setforth in claim 26, wherein the order message comprises creditauthorization information.
 33. The method, as set forth in claim 30,wherein the contact information further comprises: a customeridentifier; an evening telephone number; and a best way to contact thecustomer information.
 34. The method, as set forth in claim 26, whereinthe vehicle configuration information further comprises: a vehicleidentifier; a stock number; an item number; a dealer identifier of adealer having the tagged vehicle in inventory; a dealer identifier of adealer selected by the user from whom to purchase the tagged vehicle; avehicle initial status indicative of whether the vehicle is new or used;and a locate search identifier specifying the selected vehicleconfiguration.
 35. The method, as set forth in claim 26, wherein theconfirmation message further comprises: an order line number; an itemnumber; a body style; an order status; and an action code.
 36. Themethod, as set forth in claim 26, the vehicle configuration comprises: aprice; a make; a model; an engine specification; a transmissionspecification; an exterior paint color; a wheel specification; a tirespecification; a seat fabric specification; an interior color; an audiosystem specification; a drive specification; a cab specification; a bodystyle specification; a rear axle ratio specification; a pay load packagespecification; a wheel base specification; a roof color; a doorspecification; an accent color; a spare tire specification; a PEPspecification; an option package specification; and a stand alonepackage specification.